Bump Velopack 0.0.1298 → 1.2.0 and pin the vpk CLI to match#1150
Merged
Conversation
Velopack 1.x is the stable line; this also corrects a latent mismatch — build.yml ran `dotnet tool install -g vpk` unpinned, so releases were already packed with vpk 1.x while the app library trailed at 0.0.1298. This aligns the reader library with the packer (now pinned to vpk 1.2.0) without changing the feed format. - Dashboard + Lite: Velopack PackageReference 0.0.1298 -> 1.2.0 - build.yml: `dotnet tool install -g vpk --version 1.2.0` (was unpinned) - Lock files regenerated (--force-evaluate); they shrink because Velopack 1.x dropped the NuGet.Versioning transitive dep (custom SemanticVersion, 1.0.1). No source changes needed — VelopackApp.Build().Run(), UpdateManager, GithubSource, CheckForUpdatesAsync/DownloadUpdatesAsync/ApplyUpdatesAndRestart all unchanged. Build clean (0 new warnings); Lite 524 + Dashboard 487 green. Live cross-release auto-update to be validated at the next release (checklist 8b). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Moves the auto-update framework to the Velopack 1.x stable line, and corrects a latent mismatch:
build.ymlrandotnet tool install -g vpkunpinned, so releases were already packed with vpk 1.x while the app library trailed at 0.0.1298. This aligns the reader library with the packer (now pinnedvpk --version 1.2.0) without changing the feed format.Changes
Velopack0.0.1298 → 1.2.0build.yml:dotnet tool install -g vpk --version 1.2.0(was unpinned)--force-evaluate); they shrink — Velopack 1.x dropped theNuGet.Versioningtransitive dep (customSemanticVersion, since 1.0.1).No source changes needed
VelopackApp.Build().Run(),UpdateManager,GithubSource,CheckForUpdatesAsync/DownloadUpdatesAsync/ApplyUpdatesAndRestartall unchanged at the API level.Verification
Build clean (0 new warnings); Lite 524 + Dashboard 487 green.
Follow-up
The live cross-release auto-update path can only be fully validated at an actual tagged release — covered by the new §8b release-checklist step (Help → About → download → restart). Since the feed was already vpk-1.x-generated, this bump reduces rather than adds update-path risk.
🤖 Generated with Claude Code